Skip to content

RELEASE: Releasing 10 package(s) (main)#15787

Merged
vmoroz merged 1 commit intomainfrom
prepare-release/main
Mar 17, 2026
Merged

RELEASE: Releasing 10 package(s) (main)#15787
vmoroz merged 1 commit intomainfrom
prepare-release/main

Conversation

@azure-pipelines
Copy link
Contributor

@azure-pipelines azure-pipelines bot commented Mar 16, 2026

This PR was auto-generated by prepare-release. When ready to release, merge this PR into main. If not ready yet, this PR will be updated as more changes merge.

Packages to Release (10)

@react-native-windows/automation@0.0.0-canary.1037

  • Bump @react-native-windows/automation-channel to v0.0.0-canary.1037

@react-native-windows/automation-channel@0.0.0-canary.1037

  • Bump react-native-windows to v0.0.0-canary.1037

@react-native-windows/automation-commands@0.0.0-canary.1037

  • Bump @react-native-windows/automation-channel to v0.0.0-canary.1037

@react-native-windows/tester@0.0.1

  • Bump react-native-windows to v0.0.0-canary.494

@rnw-scripts/debug-test@0.0.0

  • Bump @react-native-windows/automation to v0.3.14

@rnw-scripts/e2e-test-app-fabric@0.0.0

  • (dependency update)

@rnw-scripts/playground@0.0.54

  • Bump react-native-windows to v0.0.0-canary.494

@rnw-scripts/sample-app-fabric@0.0.1

  • (dependency update)

@rnw-scripts/sample-custom-component@0.0.1

  • (dependency update)

react-native-windows@0.0.0-canary.1037

  • Speed up the publish pipeline
  • Fix unhandled synchronous throw from ConnectAsync
  • Try fixing the circular dependency error

@azure-pipelines azure-pipelines bot requested a review from a team as a code owner March 16, 2026 20:50
@vmoroz
Copy link
Member

vmoroz commented Mar 16, 2026

/azp run

@azure-pipelines
Copy link
Contributor Author

Azure Pipelines successfully started running 2 pipeline(s).

@vmoroz vmoroz enabled auto-merge (squash) March 16, 2026 22:25
@azure-pipelines azure-pipelines bot force-pushed the prepare-release/main branch from 1811ec2 to 7255de3 Compare March 16, 2026 23:16
@vmoroz
Copy link
Member

vmoroz commented Mar 17, 2026

/azp run

@azure-pipelines
Copy link
Contributor Author

Azure Pipelines successfully started running 2 pipeline(s).

@azure-pipelines azure-pipelines bot force-pushed the prepare-release/main branch from 7255de3 to 76143e9 Compare March 17, 2026 03:06
@vmoroz
Copy link
Member

vmoroz commented Mar 17, 2026

/azp run

@azure-pipelines
Copy link
Contributor Author

Azure Pipelines successfully started running 2 pipeline(s).

@vmoroz vmoroz disabled auto-merge March 17, 2026 03:32
@azure-pipelines azure-pipelines bot force-pushed the prepare-release/main branch from 76143e9 to b08a1c0 Compare March 17, 2026 05:13
@vmoroz vmoroz enabled auto-merge (squash) March 17, 2026 17:30
@vmoroz
Copy link
Member

vmoroz commented Mar 17, 2026

/azp run

@azure-pipelines
Copy link
Contributor Author

Azure Pipelines successfully started running 2 pipeline(s).

@azure-pipelines azure-pipelines bot force-pushed the prepare-release/main branch from b08a1c0 to 8470d26 Compare March 17, 2026 18:16
@azure-pipelines azure-pipelines bot force-pushed the prepare-release/main branch from 8470d26 to 104b4b4 Compare March 17, 2026 18:21
@vmoroz
Copy link
Member

vmoroz commented Mar 17, 2026

/azp run

@azure-pipelines
Copy link
Contributor Author

Azure Pipelines successfully started running 2 pipeline(s).

@vmoroz vmoroz merged commit 1937d30 into main Mar 17, 2026
47 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants